Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
500-tree-1
name
1600
tree-preservation-order

undefined

500-tpo-1
uprn
address-text
point
POINT (-1.037092 50.886521)
geometry
MULTIPOLYGON (((-1.037035 50.886515,-1.037038 50.886526,-1.037046 50.886536,-1.037058 50.886544,-1.037074 50.886549,-1.037092 50.886551,-1.037109 50.886550,-1.037125 50.886545,-1.037138 50.886537,-1.037146 50.886527,-1.037149 50.886516,-1.037147 50.886505,-1.037139 50.886495,-1.037126 50.886487,-1.037111 50.886481,-1.037093 50.886479,-1.037075 50.886481,-1.037060 50.886486,-1.037047 50.886494,-1.037038 50.886504,-1.037035 50.886515)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL